Investing in Software Sustainment

In many government weapon systems, sustaining software depends heavily on organic engineering efforts. This is different from hardware sustainment (the more traditional form of sustainment), which often depends heavily on the supply chain and service providers and much less on engineering capability. Because of this shift, a larger portion of sustainment funding needs to be allocated to improving the sustainment infrastructure within government sustainment organizations. This includes the engineering processes, tools, and skills of engineering staff. Failure to recognize this need in a timely fashion has the potential to increase sustainment costs and, at the same time, degrade system performance. The decisions and processes are complex because various stakeholders make decisions at different times, yet these decisions are interrelated, impact one another, and create constraints on the ability of the sustainment organization to fulfill its mission. To deal with the complexity of the decision-making process, the Software Engineering Institute (SEI) developed a simulation model for analyzing the effects of changes in demand for software sustainment and the corresponding funding decisions. The model allows decision-makers to analyze multiple allocation strategies in response to changes from mission command and budget authorities. The model has been tested and calibrated using historical data and is now in operational use by the Process Resource Team at the Naval Air Weapons Station China Lake. Introduction The ideas for this model were developed in response to real-world events. One DoD program charged with sustaining a 20+ year old aircraft system asked the SEI how it could justify the capital investment necessary to update its test and support systems and the supply chain. Some of the parts were past end-of-life, making them difficult to source, and the radar—a major technology component—had been updated without updating the test equipment. The situation was placing a major strain on the organization. Engineers had to spend significant work time on eBay buying parts. Radar testing costs escalated significantly because of the new steps required: 1 Copyright 2015 Carnegie Mellon University. No warranty. This Carnegie Mellon University and Software Engineering Institute material is furnished on an “as-is” basis. Carnegie Mellon University makes no warranties of any kind, either expressed or implied, as to any matter including, but not limited to, warranty of fitness for purpose or merchantability, exclusivity, or results obtained from use of the material. Carnegie Mellon University does not make any warranty of any kind with respect to freedom from patent, trademark, or copyright infringement. This material has been approved for public release and unlimited distribution. DM-0002313.